@slawekjaranowski Please review.

I think we need some kind of a commit freeze in order to commit this -- too many changes.

I have worked a little on site output.

Please check by:

mvn site site:stage

and investigate output in target/staging/versions

I have worked a little on site output.

Please check by:

mvn site site:stage

and investigate output in target/staging/versions

Maven site won't build anymore on Github.

Error: Failed to execute goal on project versions-maven-plugin: Could not resolve dependencies for project org.codehaus.mojo:versions-maven-plugin:maven-plugin:2.14.0-SNAPSHOT: The following artifacts could not be resolved: org.codehaus.mojo.versions:model-ruleset:jar:2.14.0-SNAPSHOT, org.codehaus.mojo.versions:model-report:jar:2.14.0-SNAPSHOT: Could not find artifact org.codehaus.mojo.versions:model-ruleset:jar:2.14.0-SNAPSHOT in ossrh-snapshots (https://oss.sonatype.org/content/repositories/snapshots) -> [Help 1]

Looks like maven site requires the artifacts to be present in the local repo. So we need to do install -P run-its instead of verify in maven-verify.yml?

By the way, why did you remove the XSD schemas of the reports from the XSD section? I can re-add those unless you explicitly wanted those removed...

By the way, why did you remove the XSD schemas of the reports from the XSD section? I can re-add those unless you explicitly wanted those removed...

I moved it to place where is generated ... for old versions of XSD we will need place a copy in root site to preserver old path.
We will change repo name ... 😄

Looks like maven site requires the artifacts to be present in the local repo. So we need to do install -P run-its instead of verify in maven-verify.yml?

I see - we use under site build current version of plugin ... it is tricky and sometime works, but with more dependencies for another module can stop working ...

To be clear we should used previous version of plugin for site build.

Looks like maven site requires the artifacts to be present in the local repo. So we need to do install -P run-its instead of verify in maven-verify.yml?

I see - we use under site build current version of plugin ... it is tricky and sometime works, but with more dependencies for another module can stop working ...

To be clear we should used previous version of plugin for site build

But that won't work - the previous version doesn't have modules 😏

Instead, why don't we do something like an extra Github Ci job before running site - Install with no tests, no enforcer, no chesktyle etc. Or compose that as an extra goal in the Site job?

I changed to instal for first step build ... I'm waiting for build ...

I'm want to go with this PR ... even more I can update site with snapshot version before release, so we can quickly resolve all site issues.

Next PR like enforcer rule can be put in separate module - What do you think?

I'm want to go with this PR ... even more I can update site with snapshot version before release, so we can quickly resolve all site issues.

Next PR like enforcer rule can be put in separate module - What do you think?

Definitely!

Can we merge?

So, merged ... next release will be very interesting 😄

eeeh I forgot to squash 😠